- Introduced unit tests for `WellInventoryRow` alias mappings.
- Verified correct handling of alias fields like `well_hole_status`, `mp_height_ft`, and others.
- Ensured canonical fields take precedence when both alias and canonical values are provided.

… and new fields

- Added `flexible_lexicon_validator` to support case-insensitive validation of enum-like fields.
- Introduced new fields: `OriginType`, `WellPumpType`, `MonitoringStatus`, among others.
- Updated existing fields to use flexible lexicon validation for improved consistency.
- Adjusted `WellInventoryRow` optional fields handling and validation rules.
- Refined contact field validation logic to require `role` and `type` when other contact details are provided.

…dations

- Refined validation error handling to provide more detailed feedback in test assertions.
- Adjusted test setup to ensure accurate validation scenarios for contact and water level fields.
- Updated contact-related tests to validate new composite field error messages.

- Renamed "Water" to "Water Bearing Zone" and refined its definition.
- Added new term "Water Quality" under `note_type` category.

…story updates

… to prevent cross-test collisions

- Supports BDD test suite stability
- Added hashing mechanism to append unique suffix to `well_name_point_id` for scenario isolation.
- Integrated pandas for robust CSV parsing and content modifications when applicable.
- Ensured handling preserves existing format for IDs ending with `-xxxx`.
- Maintained existing handling for empty or non-CSV files.

…ollback side effects

- Supports transaction management
- Moved `session.refresh` calls under `commit` condition to streamline database session operations.
- Reorganized `session.rollback` logic to properly align with commit flow.

…ory source fields in support of schema alignment and database mapping

- Update well inventory CSV files to correct data inconsistencies and improve schema alignment.
- Added support for `Sample`, `Observation`, and `Parameter` objects within well inventory processing.
- Enhanced elevation handling with optional and default value logic.
- Introduced `release_status`, `monitoring_status`, and validation for derived fields.
- Updated notes handling with new cases and refined content categorization.
- Improved `depth_to_water` processing with associated sample and observation creation.
- Refined lexicon updates and schema field adjustments for better data consistency.

…h 1 well

- Updated BDD tests to reflect changes in well inventory bulk upload logic, allowing the import of 1 well despite validation errors.
- Modified step definitions for more granular validation on imported well counts.
- Enhanced error message detail in responses for validation scenarios.
- Adjusted sample CSV files to match new import logic and validation schema updates.
- Refined service behavior to improve handling of validation errors and partial imports.

… unique well name suffixes in well inventory scenarios

- Updated `pd.read_csv` calls with `keep_default_na=False` to retain empty values as-is.
- Refined logic for suffix addition by excluding empty and `-xxxx` suffixed IDs.
- Improved test isolation by maintaining scenario-specific unique identifiers.

…nd `DataQuality`

- Changed `SampleMethodField` to validate against `SampleMethod` instead of `OriginType`
- Changed `DataQualityField` to validate against `DataQuality` instead of `OriginType`

… import

- Make contact.role and contact.contact_type nullable in the ORM and migrations
- Update contact schemas and well inventory validation to accept missing values
- Allow contact import when name or organization is present without role/type

- Stop round-tripping CSV fixtures through pandas to avoid rewriting structural test cases
- Preserve repeated header rows and duplicate column fixtures so importer validation is exercised correctly
- Keep the blank contact name/organization scenario focused on a single invalid row for stable assertions

…n errors

- Prevent one actual validation error from satisfying multiple expected assertions (avoids false positives)
- Keep validation matching order-independent while requiring distinct matches (preserves flexibility)
- Tighten BDD error checks without relying on exact error text (improves test precision)

…behavior

- Update partial-success scenarios to expect valid rows to import alongside row-level validation errors
- Reflect current importer behavior for invalid lexicon, invalid date, and repeated-header cases
- Keep BDD coverage focused on user-visible import outcomes instead of outdated all-or-nothing assumptions

…sitive parsing

- Update unit expectations to accept lowercase placeholder tokens that are now supported
- Document normalization of mixed-case and spaced placeholder formats to uppercase prefixes
- Keep test coverage aligned with importer behavior and reduce confusion around valid autogen inputs

…DataQuality`

- Adjust test data to reflect updated descriptions for `sample_method` and `data_quality` fields.

…ization scenarios

- Add test to ensure contact creation returns None when both name and organization are missing
- Add test to verify contact creation with organization only, ensuring proper dict structure
- Update assertions for comprehensive validation of contact fields

…ates_v2

…s for Sample and Observation

- Replace `name_point_id` with `name` in `sample_name` generation
- Rename `observation_*` fields for consistency with updated schemas

- Adjust `content.decode` to use `utf-8-sig` for correct header parsing of UTF-8 files with BOM
- Prevent encoding issues when processing imported files

…h-to-water is blank

- Treat blank depth_to_water_ft values as missing instead of invalid numeric input
- Create water-level sample and observation records when water_level_date_time is present even if no depth value was obtained
- Preserve attempted measurements for dry, obstructed, or otherwise unreadable wells without dropping the observation record

…rganization terms

- Treat blank contact organization and well status values as missing instead of persisting empty strings
- Prevent foreign key failures caused by empty organization and status lexicon references during import
- Add newly encountered organization terms to the lexicon so valid contact records can persist successfully

- Detect previously imported well inventory rows before inserting related records
- Skip recreating field activity water-level samples and observations when the same row is reprocessed
- Return serializable existing-row results so CLI reruns report cleanly instead of crashing

…e-database-errors

kas-BDMS-626-resolve-database-errors

Each contact should have a role and contact_type

…tailed DB errors

Jab bdms 626